Compliance voltage monitoring and adjustment in an implantable medical device

ABSTRACT

An architecture is disclosed for an Implantable Pulse Generator having improved compliance voltage monitoring and adjustment software and hardware. Software specifies which stimulation pulses are to be measured as relevant to monitoring and adjusting the compliance voltage. Preferably, specifying such pulses occurs by setting a compliance monitoring instruction (e.g., a bit) in the program that defines the pulse, and the compliance monitor bit instruction may be set at a memory location defining a particular pulse phase during which the compliance voltage should be monitored. When a compliance monitor instruction issues, the active electrode node voltages are monitored and compared to desired ranges to determine whether they are high or low. Compliance logic operates on these high/low signals and processes them to decide whether to issue a compliance voltage interrupt to the microcontroller, which can then command the compliance voltage generator to increase or decrease the compliance voltage.

CROSS-REFERENCE TO RELATED APPLICATIONS

This non-provisional application is based on U.S. Provisional Patent Application Ser. Nos. 62/425,765, filed Nov. 23, 2016, and 62/386,000, filed Sep. 10, 2016. These applications are incorporated by reference in their entireties, and priority is claimed to both.

FIELD OF THE INVENTION

The present invention relates generally to implantable medical devices, and more particularly to improved compliance voltage monitoring and adjustment in an implantable pulse generator.

INTRODUCTION

Implantable stimulation devices are devices that generate and deliver electrical stimuli to body nerves and tissues for the therapy of various biological disorders, such as pacemakers to treat cardiac arrhythmia, defibrillators to treat cardiac fibrillation, cochlear stimulators to treat deafness, retinal stimulators to treat blindness, muscle stimulators to produce coordinated limb movement, spinal cord stimulators to treat chronic pain, cortical and deep brain stimulators to treat motor and psychological disorders, and other neural stimulators to treat urinary incontinence, sleep apnea, shoulder subluxation, etc. The description that follows will generally focus on the use of the invention within a Spinal Cord Stimulation (SCS) system, such as that disclosed in U.S. Pat. No. 6,516,227. However, the present invention may find applicability in any implantable medical device system, including a Deep Brain Stimulation (DBS) system.

As shown in FIGS. 1A-1C, an SCS system typically includes an Implantable Pulse Generator (IPG) 10, which includes a biocompatible device case 12 formed of a conductive material such as titanium for example. The case 12 typically holds the circuitry and power source (e.g., battery) 14 (FIG. 1C) necessary for the IPG 10 to function, although IPGs can also be powered via external RF energy and without a battery. The IPG 10 is coupled to electrodes 16 via one or more electrode leads 18, such that the electrodes 16 form an electrode array 20. The electrodes 16 are carried on a flexible body 22, which also houses the individual signal wires 24 coupled to each electrode. In the illustrated embodiment, there are eight electrodes (Ex) on two leads 18 for a total of sixteen electrodes 16, although the number of leads and electrodes is application specific and therefore can vary. The leads 18 couple to the IPG 10 using lead connectors 26, which are fixed in a non-conductive header material 28, which can comprise an epoxy for example.

As shown in the cross-section of FIG. 1C, the IPG 10 typically includes a printed circuit board (PCB) 30, along with various electronic components 32 mounted to the PCB 30, some of which are discussed subsequently. Two coils (more generally, antennas) are shown in the IPG 10: a telemetry coil 34 used to transmit/receive data to/from an external controller (not shown); and a charging coil 36 for charging or recharging the IPG's battery 14 using an external charger (not shown). FIG. 1B shows these aspects in perspective with the case 12 removed for easier viewing. Telemetry coil 34 may alternatively comprise a short range RF antenna for wirelessly communicating in accordance with a short-range RF standard such as Bluetooth, WiFi, MICS, Zigbee, etc., as described in U.S. Patent Application Publication 2016/0051825.

FIGS. 2A and 2B show an architecture 140 for the circuitry in IPG 10, which is disclosed in U.S. Provisional Patent Application Ser. Nos. 62/386,000 (“the '000 application”) and 62/393,003 (“the '003 application”), both filed Sep. 10, 2016, and both of which are incorporated by reference in their entireties. Architecture 140 includes at least one Application Specific Integrated Circuit (ASIC) 160. ASIC 160 includes a microcontroller block 150, which as shown in FIG. 2B can communicate with other functional blocks in the ASIC 160 via internal bus 192. Because ASIC 160 includes an internal microcontroller 150, an external microcontroller can be dispensed with in the improved architecture 140, simplifying IPG design and saving room within the interior of the case 12 and on the IPG's PCB 30 (FIG. 1C). In one example, the microcontroller block 150 can comprise circuitry from an ARM Cortex-M0+ Processor, which may be incorporated into the monolithic integrated circuit of the ASIC 160 by licensing various necessary circuits from the library that comprises that processor. ASIC 160 can comprise a monolithic integrated circuit formed on its own semiconductive substrates (“chip”), and may be contained in its own package and mounted to the IPG 10's PCB 30.

Even though ASIC 160 includes a microcontroller block 150, the ASIC 160 may still couple to an external bus 190. This can facilitate communications between the ASIC 160 and another device, such as a memory integrated circuit (not shown) or possibly another microcontroller device that might be coupled to the bus 190 as explained in the above-incorporated '000 and '003 applications. External bus 190 can also facilitate communication between (master) ASIC 160 and another identically-constructed (slave) ASIC 160′, shown in dotted lines in FIG. 2A. Use of an additional ASIC 160′ allows the number of electrodes 16 the IPG 10 supports to be doubled, for example from sixteen to thirty two, or thirty two to sixty four. Off-bus connections 54 can facilitate master/slave interaction between ASICs 160 and 160′, and as explained in detail in the above-incorporated '000 and '003 applications.

FIG. 2B shows various functional circuit blocks within ASIC 160 in addition to the microcontroller block, which are briefly described. As mentioned, ASIC 160 includes an internal bus 192, and each of the functional blocks includes interface circuitry 88 enabling communication on the internal bus 192. Interface circuitry 88 helps each block recognize when microcontroller block 150 is communicating addresses pertaining to that block via bus 192.

ASIC 160 contains several terminals 61 (e.g., pins, bond pads, solder bumps, etc.), such as those necessary to connect to the external bus 190, the battery 14, the coils 34, 36, external memory (not shown), etc. ASIC terminals 61 include electrode nodes 61 a (E1′-E16′ and Ec′) which circuit nodes are also present on the PCB 30 (FIG. 1C) inside of the IPG's case 12. The electrode nodes 61 a connect to the electrodes 16 (E1-E16) on the lead(s) 18 outside of the case 12 by way of DC-blocking capacitors 55. As is known, DC-blocking capacitors 55 are useful to ensure that DC current isn't inadvertently (e.g., in the event of failure of the ASIC 160's circuitry) injected into the patient's tissue, and hence provide safety to the IPG 10. Such DC-blocking capacitors 55 can be located on or in the IPG 10's PCB 30. See U.S. Patent Application Publication 2015/0157861. Note that there is also an electrode node 61 a Ec′ which is connected to the case 12 (preferably by a DC-blocking capacitor 55), thus allowing the case 12 to operate as an electrode 16 (Ec). ASIC 160 may support other numbers or types of electrode nodes/electrodes (e.g., thirty-two electrodes E1-E32 plus the case Ec).

Each of the circuit blocks in ASIC 160 performs various functions in IPG 10. Telemetry block 64 couples to the IPG telemetry coil 34, and includes transceiver circuitry for wirelessly communicating with an external device according to a telemetry protocol. Such protocol may comprise Frequency Shift Keying (FSK), Amplitude Shift Keying (ASK), or various short-range RF standards such as those mentioned above. Charging/protection block 62 couples to the IPG charging coil 38, and contains circuitry for rectifying power wirelessly received from an external charger (not shown), and for charging the battery 14 in a controlled fashion.

Analog-to-Digital (A/D) block 66 digitizes various analog signals for interpretation by the IPG 10, such as the battery voltage Vbat, the compliance voltage VH (discussed in detail below), or voltages appearing at the electrodes, and is coupled to an analog bus 67 containing such voltages. A/D block 66 may further receive signals from sample and hold block 68. For example, sample and hold circuitry 68 may determine a voltage difference between two electrode nodes, which voltage difference may then be digitized at A/D block 66. Knowing the difference in voltage between two electrodes when they pass a constant current allows for a determination of the (tissue) resistance between them, which is useful for a variety of reasons.

Clock generation block 74 can be used to generate a clock for the ASIC 160 and communication on the bus 192. Clock generation block 74 may receive an oscillating signal from an off-chip crystal oscillator 56, or may comprise other forms of clock circuitry located completely on chip, such as a ring oscillator. U.S. Patent Application Publication 2014/0266375 discloses another on-chip circuit that can be used to generate a clock signal on the ASIC 160.

Master/slave control block 86 can be used to inform the ASIC 160 whether it is to be used as a master ASIC or as a slave ASIC (e.g., 160 or 160′ in FIG. 2A), which may be bond programmed at M/S terminal 61. For example, M/S terminal may be connected to a power supply voltage (e.g., Vbat) to inform ASIC 160 that it will operate as a master ASIC, or to ground to inform that it will operate as a slave 160′, in which case certain functional blocks will be disabled, as the above-cited references explain.

Nonvolatile memory (NOVO) block 78 caches any relevant data in the system (such as log data). Additional memory (not shown) can also be provided off-chip via a serial interface block 84.

ASIC 160 further includes a stimulation circuitry block 170 (FIG. 2B), which includes circuitry for receiving and storing stimulation parameters from the microcontroller block 150 via bus 192. Stimulation parameters define the shape and timing of stimulation pulses to be formed at the electrodes, and can include parameters such as which electrodes E1-E16 or Ec will be active; whether those active electrodes are to act as anodes that source current to a patient's tissue, or cathodes that sink current from the tissue; and the amplitude (A), duration (D), and frequency (f) of the pulses. Amplitude may comprise a voltage or current amplitude. Such stimulation parameters may be stored in registers in the stimulation circuitry block 170. See, e.g., U.S. Patent Application Publications 2013/0289661; 2013/0184794.

Simulation circuitry block 170 also includes a Digital-to-Analog Converter (DAC) 172 for receiving the stimulation parameters from the registers and for forming the prescribed pulses at the selected electrodes. FIG. 3 shows a simple example of DAC circuitry 172 operating to provide current pulses between selected electrodes E1 and E2 and through a patient's tissue, Rt. DAC circuitry 172 as shown comprises two portions, denoted as PDAC 172 p and NDAC 172 n. These portions of DAC circuitry 172 are so named because of the polarity of the transistors used to build them and the polarity of the currents they provide. Thus, PDAC 172 p is formed primarily from P-channel transistors and is used to source a current +I to the patient's tissue Rt via a selected electrode E1 operating as an anode. NDAC 172 n is formed primarily from N-channel transistors and is used to sink current −I from the patient's tissue via a selected electrode E2. It is important that current sourced to the tissue at any given time equal that sunk from the tissue to prevent charge from building in the tissue, although more than one anode electrode and more than one cathode electrode may be operable at a given time.

PDAC 172 p and NDAC 172 n receive digital control signals from the registers in the stimulation circuitry block 170, generically denoted <Pstim> and <Nstim> respectively, to generate the prescribed pulses with the prescribed timing and amplitude. In the example shown, PDAC 172 p and NDAC 172 n comprise current sources, but could comprise voltage sources as well. The DAC circuitry 172 (PDAC 172 p and NDAC 172 n) may be dedicated at each of the electrodes, and thus may be activated only when its associated electrode is selected as an anode or cathode. See, e.g., U.S. Pat. No. 6,181,969. Alternatively, the current produced by one or more DACs (or one or more current sources or sinks within a DAC) may be distributed to a selected electrode by a switch matrix (not shown), in which case optional control signals <Psel> and <Nsel> would be used to control the switch matrix and establish the connection between the selected electrode and a current source or sink. See, e.g., U.S. Pat. No. 8,606,362. DAC circuitry 172 may also use a combination of these dedicated and distributed approaches. See, e.g., U.S. Pat. No. 8,620,436.

The PDAC 172 p and NDAC 172 n along with the intervening tissue Rt complete a circuit between a power supply VH, called the compliance voltage, and ground. The compliance voltage VH is preferable adjustable to an optimal level at compliance voltage generator block 76 (FIG. 2B) to ensure that current pulses of a prescribed amplitude can be produced without unnecessarily wasting IPG power. Such adjustment may occur by measuring voltage drops across the PDAC (Vp) and NDAC (Vn) circuitry as they are forming a pulse. The measured voltage drops can be used to ensure that the compliance voltage VH produced is optimal for the stimulation current being provided—i.e., VH is not too low to be unable to produce the current required for the stimulation, nor too high so as to waste power in the IPG 10. Compliance voltage generator block 76 includes circuitry for boosting a power supply voltage such as the battery voltage, Vbat, to a proper level for VH. Such boost circuitry (components of which may be located off chip) can include an inductor-based boost converter or a capacitor-based charge pump.

In the example waveform shown in FIG. 3, the pulses provided at the electrodes are biphasic, meaning that each pulse comprises a first phase 94 a of a first polarity, followed by a second phase 94 b of an opposite polarity. This is useful as a means of active recovery of charge that may build up on the DC-blocking capacitors 55. Thus, while charge will build up on the capacitors 55 during the first pulse phase 94 a, the second pulse phase 94 b will actively recover that charge, particularly if the total amount of charge is equal in each phase (i.e., of the area under the first and second pulse phases are equal). Recovery of excess charge on the DC-blocking capacitors 55 is desirable to ensure that the DAC circuitry 172 will operate as intended: if the charge across the DC-blocking capacitors 55 is not zero at the end of each pulse, such remaining charge may impact formation of subsequent pulses, or other problems may occur, as discussed further below.

While active recovery of charge using a biphasic pulse is beneficial, such active recovery may not be perfect, and hence some residual charge may remain on the DC-blocking capacitors 55 even after completion of the second phase 94 b of the biphasic pulse. Passive charge recovery may therefore be employed that does not involve use of active currents provided by the DAC circuitry 172. Passive charge recovery is implemented within the stimulation circuitry block 170, and includes use of passive recovery switches (e.g., transistors) 96(x), each connected between one of the electrode nodes (Ex′ and Ec′) 61 a and a common reference voltage. This common reference voltage as shown may simply comprise the voltage, Vbat, of the battery 14 as (FIG. 1C) as shown, but another reference voltage could also be used, such as the compliance voltage VH described earlier, a midpoint voltage such as VH/2, ground (GND), or some other value. A variable resistor 97 is connected in series to each of the passive recovery switches 96 between the electrodes nodes 61 a and the common reference voltage (e.g., Vbat) to set the rate of passive discharge. See e.g., U.S. Provisional Patent Application Ser. No. 62/393,007 (“the '007 application”), filed Sep. 10, 2016 (discussing advents related to passive recovery).

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C show an Implantable Pulse Generator (IPG), and the manner in which an electrode array is coupled to the IPG, in accordance with the prior art.

FIG. 2A shows an architecture for an IPG utilizing at least one Application Specific Integrated Circuit (ASIC), and FIG. 2B shows circuitry blocks within the ASIC and connection to off-chip components.

FIG. 3 shows aspects of the Digital-to-Analog Converters (DACs) within the stimulation circuitry of the ASIC, and stimulation pulses formable thereby.

FIGS. 4A-4D show further details of the stimulation circuitry and DAC circuitry.

FIG. 5A shows a pulse train issued according to a first aggregate program (FIG. 5C) associating a pulse program and a steering program (FIG. 5B) in a first timing channel, while FIG. 5D shows a different pulse train issued according to a second aggregate program in a second timing channel. In both aggregate programs, a compliance monitoring bit is set to enable a compliance voltage measurement during some of the pulses.

FIG. 6A shows inclusion of a compliance detector within the ASIC 160. FIGS. 6B-6D show details of the compliance detector.

FIG. 7A shows operation of the microcontroller within the ASIC upon receiving an interrupt from the compliance detector to adjust the compliance voltage. FIGS. 7B and 7C show adjustment of different types of compliance voltage generators.

DETAILED DESCRIPTION

Before discussing compliance voltage monitoring and adjustment, which are the focus of this disclosure, further details concerning the stimulation circuitry 170 and its DAC circuitry 172 are shown in FIGS. 4A-4D. This is done for completeness, and to show an example implementation in which the compliance voltage monitoring and adjustment aspects of this disclosure can operate. Still further details concerning these circuitries can be found in the above-incorporated '000 and '003 applications, with which the reader is assumed familiar. Note however that implementations of the invention are not limited to any particular stimulation circuitry 170 or DAC circuitry 172 implementation.

As shown in FIG. 4A, stimulation circuitry 170 includes memory circuitry that stores microcode processed by one or more pulse definition circuits (PDCs) 171, which operate as control circuits to generate the control signals that are sent to the DAC circuitry 172. Memory circuitry includes a steering memory 502 that contains electrode steering programs, and a pulse memory 504 that contains pulse programs, both of which are discussed further with respect to FIG. 5B. Memory circuitry also includes an aggregate memory 506 that contains aggregate programs that link or associate one or more pulse programs and one or more steering programs to create a desired stimulation pulse therapy program, as discussed further with respect to FIG. 5C. The stimulation circuitry 170 additionally includes a configuration memory 508 that stores configuration parameters, some of which are global and applied across all PDCs 171, and some of which are specific to a particular PDC 171. The memories 502, 504, 506, and 508 can be read from and written to by the microcontroller 150. Each location (e.g., each 32-bit location) in the memory circuitry may be formed as a register of multiple flip-flops or as an addressable location in a more typical memory, and may comprise separate memory circuits or a single memory circuit.

Stimulation circuitry 170, as well as comprising memory circuitry, can comprise logic circuitry. Such logic circuitry may include standard logic processing circuitry, such as CMOS logic gates, Arithmetic Logic Unit (ALU) circuitry, Digital Signal Processing (DSP) circuitry, Programmable Logic Array (PLA) circuitry, Field Programmable Gate Array (FPGA) circuitry, etc. Programming of such logic circuitry—i.e., algorithms operable in the stimulation circuitry 170 and the compliance logic 220 as described herein (FIG. 6A)—may comprise microcode or firmware that can be read and processed by such logic circuitry.

Each of the PDCs 171(1)-(4) are used in a normal mode (in which control signal K=‘0’) to control the formation of stimulation pulses within a timing channel, and hence stimulation circuitry 170 as shown in FIG. 4A supports four such timing channels (TC1-TC4). As explained in further detail in the '000 application, pulse logic 514 in each PDC 171(x) creates pulse amplitude control signals <Jpx> and <Jnx>, which are sent to the DAC circuitry 172. More specifically, and referring to FIG. 4B, pulse amplitude control signals <Jpx> and <Jnx> are respectively sent by a PDC 171(x) to a particular PDACx/NDACx pair associated with each PDCx/timing channel (TCx) to set the magnitude of the pulses that are respectively sourced to or sunk from the electrodes selected in that timing channel. Thus, PDAC1 receives <Jp1> to set the amplitude of current sourced in timing channel 1 (TC1), while NDAC1 receives <Jn1> to set the amplitude of current sunk in TC1. Likewise, PDAC2 receives <Jp2> to set the amplitude of current sourced in TC2, while NDAC2 receives <Jn2> to set the amplitude of current sunk in TC2, etc. <Jpx> and <Jnx> within a timing channel may comprise the same value, and may be more simply referred to as <Jx>

Referring again to FIG. 4A, which electrodes are selected in each timing channel are determined using steering logic 512 (which reads data from the steering memory 502), aggregate logic 516 (which reads data from the aggregate memory 506), and the pulse logic 514. This will be described later with respect to FIGS. 5B and 5C. Ultimately, the steering logic 512 in each PDC 171 outputs to an electrode combiner 520 which determines which switches 178 (FIGS. 4C and 4D) are to be closed in which PDACs and NDACs. Specifically, the electrode combiner 520 issues switch control signals <Cpx> for the PDACx associated with PDC 171(x)/TCx, and switch control signals <Cnx> for the NDACx associated with PDC 171(x)/TCx, as shown in FIG. 4B.

To summarize, in a normal mode (K=0), and as shown in FIG. 4B, the DAC circuitry 172, which constitutes PDAC circuitry 172 p and NDAC circuitry 172, is organized into PDACx/NDACx pairs, each for producing stimulation pulses in a timing channel TCx. While four pairs/timing channels are shown in FIG. 4B, more or less could be supported. Notice that each PDAC and NDAC outputs to and is connected to the electrode nodes 61 a. These electrode node outputs 61 a are in turn connected to the electrodes 16 (e.g., E1-E16 and Ec) via DC-blocking capacitors 55 as described earlier. Note further that the PDACs are powered by power supply voltages VH (the compliance voltage that is the focus of this disclosure) and Vssh, which respectively define upper and lower power supply voltages for the PDACs, while the NDACs are powered by power supply voltages Vcc and ground (GND), which respectively define upper and lower power supply voltages for the NDACs. The benefits provided by these different power supply domains is discussed further in U.S. Provisional Patent Application Ser. No. 62/393,005 (“the '005 application”), filed Sep. 10, 2016, and are not discussed further.

FIG. 4C shows circuitry for one of the NDACs (NDAC1), while FIG. 4D shows circuitry for one of the PDACs (PDAC1); circuitry for the other PDACs and NDACs are similar. As one skilled in the art will appreciate, the circuitry for PDACs is largely “inverted” from that shown for the NDACs, and has expected differences given its difference in polarity. For example, current-producing portions of the PDACs are coupled to the compliance voltage VH, thus allowing the PDACs to source current to selected electrode nodes 61 a, and allowing their associated electrodes 16 to operate as anodes (positive current). By contrast, current-producing portions of the NDACs are coupled to ground, thus allowing the NDACs to sink current to selected electrode nodes 61 a, and allowing their associated electrodes 16 to operate as cathodes (negative current). Further, many of the transistors in the PDACs comprise P-channel devices, while these same transistors in the NDACs comprise N-channel devices. Otherwise, the PDACs and NDACs function similarly, and are controlled by analogous control signals such as <Jpx>, <Cpx>, and <Jnx> and <Cnx>, and K. (Given the difference in transistor polarities, these control signals may be active at different logic state in the PDACs and the NDACs). For simplicity, elements of the PDACs in FIG. 4D are labeled with elements numerals that correspond to analogous elements in the NDACs of FIG. 4C.

The NDACs of FIG. 4C operates as follows. A reference current, Iref is mirrored by a current-mirror configuration from transistor 173 to transistor 174, where it is passed through a reference transistor, Rc, thus forming a reference voltage Vref (=Iref*Rc) at node 163. As explained in the above-incorporated '003 application, reference transistor Rc may be adjustable to allow reference voltage Vref to be set. Preferably, Vref may equal 100 mV.

Iref is further mirrored to a master DAC 185, which amplifies Iref times a value J set by control signals <Jn1>. <Jn1> may comprise 8 control signals, therefore allowing J to be set from 1 <00000001> to 255 <11111111>. As explained in the '003 application, J sets the number of transistors 186 in the master DAC 185 into which Iref is mirrored. Amplified current J*Iref passes to a resistance block 187, with is formed of one or more resistance transistors 188, and controlled by control signal K. As explained in the '003 application, control signal K can be used to set a resolution of the current producible by the NDAC (and PDAC), but this detail can be ignored here.

The gate of resistance transistor(s) 188 is shared at node 166 as the gate of a number of branch transistors 184; 25 branch transistors 184 are shown in the example of FIG. 4C, although this number could be varied. Node 166 comprises the output of an operation amplifier (“op amp”) 168. One of the inputs to op amp comprises node 163 (Vref). The other input, node 164, is coupled to the output node 166 by feedback through the resistance block 187. Hence, the op amp 168 will force its inputs to be equal such that node 164 will be forced to equal node 163, and thus node 164 is set to Vref.

A switch matrix 190 is connected between the branch transistors 184 and an output transistors 182 connected to each electrode node 61 a. The switch matrix 190, comprising an array of switches (transistors) 178, can connect the current from any branch transistor 184 to any of the electrode nodes 61 a and hence to the electrodes 16. Such connection is established via switch matrix control signals <Cn1>. For example, asserting control signal C_(2,1) connects the second branch transistor 184(2) to electrode node E1′.

Each output transistors 182 is controlled by its own op amp 180. One input of op amp 180 is connected to node 164, which as explained earlier is forced to Vref. Given the feedback through each output transistor 182, the other inputs 191 are also forced to Vref. Vref is thus impressed across the branch transistors 184 when a switch coupled to that branch transistor is asserted; perhaps more importantly, Vref is impressed across both the resistance transistor(s) 188 and the branch transistor 184. These transistors 184 and 188 are also on to the same extent by virtue of their common gate connection at node 166. As such, the current through each branch transistors 184, Ib, will scale with the current through the resistance transistor(s) 188, J*Iref. More particularly, Ib will scale in accordance with the effective width of the transistors 184 and 188. For example, if resistance transistor(s) 188 have an effective width W1, and branch transistors 184 have a longer effective width W2, the current through the resistance transistor(s) 188 (J*Iref) will be amplified through each branch transistor 184: Ib=(W2/W1)*J*Iref.

The current from more than one branch transistor 184 can be summed at an electrode node if more than one switch matrix control signal <Cn1> associated with that electrode node is asserted; for example, if C_(1,1), C_(2,1), and C_(3,1) are asserted, the branch current Ib from branch transistors 184(1), 184(2), and 184(3) will sum at electrode node E1′. Generally speaking, if L switches 178 associated with an electrode node are asserted, the current at that electrode node will be I=(W2/W1)*L*J*Iref.

Again, operation of the PDACs (FIG. 4D) is largely similar, with some noteworthy differences. First, the power supply used in the PDACs—VH and Vssh—create a reference voltage at nodes 163, 164, and 191 equal to VH-Vref, which difference can again equal 100 mV. Because the compliance voltage VH can change—as discussed previously, and discussed in further detail below—this reference voltage will change. Vssh will also change to keep VH-Vssh to a constant difference, and control signals used to control the PDACs will comprise logic states of VH (‘1’) and Vssh (‘0’), which will likewise vary as VH changes. This is explained in detail in the above-referenced '005 application.

From the perspective of the electrode nodes 61 a, the PDACs will source a positive current, while the NDACs will sink a negative current. Note that a voltage (VE1, VE2, . . . VEc) will form at the electrode nodes 61 a when a particular electrode node is connected to a PDAC and being used to source current (as an anode) or is connected to an NDAC to sink current (as a cathode). As explained further below, these electrode node voltages will be used to monitor and potentially adjust the magnitude of the compliance voltage VH being generated.

As taught in the above-incorporated '000 application, the unique configuration of the stimulation circuitry 170 as shown in FIG. 4A allows for the efficient production of stimulation waveforms of unique shapes. FIG. 5A shows an example of a pulse train that can be produced in a particular timing channel (e.g., TC1, using PDAC 171(1) and PDAC1/NDAC1) using this stimulation circuitry. In this example, two electrodes E1 and E2 have been selected for stimulation, which occurs by selection of a particular steering program A in steering memory 502, as shown in FIG. 5B. Steering program A may be stored starting at location Y, with each location storing data for four of the electrodes. One quarter of each location (8 bits) stores the data for a particular electrode, including a bit indicating whether the electrode is to comprise an anode (‘1’) or cathode (‘0’), and up to seven bits indicating a percentage of the anodic or cathodic current that that electrode is to receive. Multiple steering programs can be stored in steering memory 502 (e.g., B starting at memory location Y′; C starting at memory location Y″), each designating a different one or more electrodes to operate as anodes and one or more electrodes to operate as cathodes, and a percentage of the total anodic and cathodic current such electrodes will receive.

Also shown in FIG. 5B are a number of pulse programs stored in pulse memory 504. Pulse programs specify the basic shape of a pulse, including amplitude (A) and duration (D) of its various phases. Example pulse program B is shown as starting at memory location X, with each successive location including data defining the shape of a successive pulse phase. Only 20 of the 32 available bits may be used at each location to define the pulse phases. As explained in the '000 application, bits 19 and 18 specify a type of pulse phase, which dictates the format of the remaining bits in that memory location. For example, pulse phase types may comprise active stimulation phases specifying a stimulation amplitude and duration, or delay phases (Del) which don't involve stimulation and thus only specify a duration. The reader can refer to the '000 application for a more complete discussion of the types of pulse phases and the various bits that are stored with each.

Of relevance to the pulse train example depicted in FIG. 5A are the active stimulation phases of a biphasic pulse, which have been bolded at memory locations X+1 and X+3. In particular, note in FIG. 5B pulse phase type ‘S’ (“stimulation”) which prescribes the amplitude (A2) and duration (D2) of the first pulse phase 94 a (FIG. 3) of a biphasic pulse, and pulse phase type ‘AR’ (“active recovery”) which prescribes the amplitude (A4) and duration (D4) of the second pulse phase 94 b. (If the biphasic pulse is symmetric, note that D2=D4 and A2=A4).

A pulse program is not limited to storing only biphasic pulses. Indeed, pulse phase types can be concatenated in any order to define pulses of non-conventional shapes. For example, although not shown, a pulse program may comprise a number of successive stimulation phases (type ‘S’) of increasing amplitudes, which would create a pulse with a rising stair-stepped shape. The above-incorporated '000 application provides still other examples of pulse shapes formable using the disclosed circuitry and software.

Any pulse program in memory 504 may be associated with any steering program in memory 502 to create pulses defined by the pulse program at the electrodes defined in the steering program, and this occurs by use of an aggregate program stored in aggregate memory 506, as shown in FIG. 5C. Each memory location of the aggregate program is formatted to specify a steering program and the starting address of a pulse program. Further, each location specifies a number of times at which a pulse (including its various phases as specified in the pulse program) will repeat. (An interrupt bit can also be set, which may be used to interrupt the microcontroller 150 for any number of purposes). Successive locations can define other pulse program/steering program associations, and pulse repeat numbers.

FIG. 5A shows the pulse train formed using the aggregate program 1 of FIG. 5C. Three pulse programs A, B, and C are successively specified in the aggregate program, whose pulses are repeated 4, 2, and 3 times respectively. The same steering program A (FIG. 5B) is associated with each pulse program in aggregate program 1, specifying use of electrode E1 and as anode, and E2 as a cathode. Notice that the aggregate program 1 repeats; although not shown, this can be affected by defining the start (Z) and end (Z+2) memory location in the configuration memory 508 (FIG. 4A).

While stimulation circuitry 170 and DAC circuitry 172 are beneficial in their ability to efficiently form and concatenate stimulation pulses of different shapes, the inventors realize that such flexibility gives rise to new challenges, in particular as concerns management of the compliance voltage, VH. As discussed earlier, adjustment of the compliance voltage VH is desirable to ensure that stimulation pulses can be reliably formed without wasting power (the battery 14) in the IPG 10.

But compliance voltage management is made difficult when the amplitude of pulses can be quickly and significantly altered, as occurs in the example of FIG. 5A. Compliance voltage measurements—such as the voltage drops across the PDAC (Vp) and NDAC (Vn) (FIG. 3)—could be taken during every stimulation pulse. But this would be difficult to manage and implement. For example, suppose measurements taken during pulse program A—when the pulse amplitudes are low-indicate that the compliance voltage VH is not too high or too low. When the first high-amplitude stimulation pulse of pulse program B issues, the compliance voltage may likely be too low, and therefore pulse program B's pulses may not issue with the prescribed amplitudes. In short, the therapy specified by the aggregate program 1 may not be reliably issued to the patient.

This problem is exacerbated when it is realized that stimulation circuitry 170 and DAC circuitry 172 support the concurrent execution of stimulation pulses in different timing channels. For example, FIG. 5D shows another example of a pulse train being issued in a second timing channel (TC2) on electrodes E4, E5, and E6 as defined by a steering program B. Different pulse programs D and E are also used, which are associated with steering program B in an aggregate program 2. Like timing channel 1 (FIG. 5A), the pulses in timing channel 2 vary significantly in amplitude, with pulse program E defining a pulse of a particularly high amplitude, which aggregate program 2 repeats only once. Because timing channels 1 and 2 run concurrently, it is not a simple matter to decide when to make measurements relevant to adjusting the compliance voltage, or how such measurements should be used to set the compliance voltage.

The inventors address this issue by providing in software the ability to specify which stimulation pulses are to be measured as relevant to monitoring and adjusting the compliance voltage. Preferably, specifying such pulses occurs by setting a compliance monitor bit in the program that defines the pulse, and more particularly the compliance monitor bit may be set at a memory location defining a particular pulse phase during which the compliance voltage should be monitored. When a compliance monitor bit is issued, the active electrode node voltages are monitored and compared to desired ranges to determine whether they are high or low. Compliance logic operates on these high/low signals and processes them to decide whether to issue a compliance voltage interrupt to the microcontroller, which can then instruct the compliance voltage generator to increase or decrease the compliance voltage.

Defining in software which pulses (or more generally, pulse phases) are to be measured as relevant to compliance voltage monitoring and adjustment preferably occurs by inclusion of compliance voltage monitoring data, which may comprise a single compliance monitoring bit (CMB), although longer data structures could be used as well. As shown in FIG. 5B, and preferably, such compliance monitor bit may be defined in the format of certain pulse phase types in a pulse program. For example, bit 17 comprises a compliance monitor bit in certain active and delay pulse phase types, thus allowing compliance measurements to be taken during such pulse phases if desired.

The compliance monitoring bit can be set with an instruction or not, and as explained further below, the instruction is configured to instruct the compliance circuitry to process the voltages at the selected electrode nodes during the relevant pulse phase with which the instruction is stored. Compliance monitoring bit instructions are preferably in a fashion sensible for compliance voltage control. For example, in the example timing channel TC1 of FIG. 5A, notice that the compliance monitoring bit has only been set with an instruction (a logic state ‘1’) for the high amplitude pulses used in pulse program B, but has not been set with an instruction (logic state ‘0’) not for the smaller pulses in pulse programs A and C. Specifically, the compliance monitoring bit is set only during the first pulse phase 94 a of the pulses in pulse program B, which bit is circled in FIG. 5B.

The disclosed architecture also allows the timing of the issuance of the compliance monitoring bit instruction to be defined, which is important because the issuance of this bit sets the timing at which measurements relevant to the compliance voltage are made. The timing of the compliance monitoring bit instruction is shown in the magnified view at the bottom right of FIG. 5A, which timing in this example is set using the configuration memory 508 (FIG. 4A). Within this memory 508 is a compliance monitor timing register 509, which defines when the compliance monitoring bit instruction will issue during the duration of the pulse phase in which it is set. Such timing may be defined in a number of ways. For example, the compliance monitor timing register 509 may specify a percentage during the duration (e.g., D2) of the pulse phase during which the compliance monitoring bit instruction issues, with 1% specifying issuance of the bit at the beginning of the duration, and 99% specifying issuance at the end of the duration. Alternatively, register 509 can store a time offset (e.g., 1 μs) from either the beginning or end of the pulse phase at which the CMB instruction will issue. Such time offset can be quantified by other measures of time, such as a number of cycles of a clock operating with the ASIC 160. Compliance monitor bit instruction timing could also occur after the pulse phase in other examples.

It is preferred to set the timing of the issuance of the compliance monitoring bit instruction to when the compliance voltage VH is most likely to be inadequate. In the example shown in FIG. 5A, this occurs just before the end of the first pulse phase 94 a. This is the worst case for a biphasic pulses: at the end of the first pulse phase, the DC-blocking capacitors 55 (FIG. 3) will be charged to their maximum extent, and thus the voltage across them (VC1, VC2) will be at their highest. This minimizes the voltage drops across the PDAC and NDAC (Vp, Vn) for the same compliance voltage, VH, meaning that the PDAC and NDAC are at risk for having too little power to produce pulses of prescribed amplitudes. In other words, VH is mostly likely too low at this point, and hence it is important to take a compliance voltage measurement at this point to verify compliance voltage adequacy.

To summarize, compliance voltage measurements are preferably taken at times during the first timing channel TC1 when the compliance voltage VH might be expected to be most inadequate. This allows the compliance voltage to be set at a level that is high enough to reliably form the high amplitude pulses (during pulse program B). Smaller amplitude pulses (during pulse programs A and C) can be ignored during compliance monitoring (the CBM bits are not set to ‘0’, and hence no compliance monitoring instruction). The established compliance voltage will be higher than necessary to form these smaller pulses. This wastes power in the creation of these smaller pulses, but is a reasonable trade off, as it ensures that an adequate compliance voltage will be formed for all pulses, and that minimal compliance measurements and adjustment will need to be made.

Notice that timing channel TC2 of FIG. 5D has similarly defined issuance of a compliance monitoring bit instruction during the high amplitude pulse used in pulse program E, but not for the smaller pulses in pulse programs D. This is logical for the same reasons just discussed for timing channel TC1. As will be seen in further detail with respect to FIG. 6D, compliance voltage measurements can be taken during pulses (or pulse phases) in both timing channels 1 and 2. This ensures that measurements are made will be adequate to adjust the compliance voltage to be sufficient for all pulses in all timing channels. However, it isn't strictly necessary to set compliance monitor bits with instruction in pulses in all active timing channels.

Compliance monitoring instructions can be set in different ways. For example, compliance monitor bits could be set to ‘1’ by a user writing the pulse program or the aggregate program which calls it to provide therapy to a patient. This would most likely be done with the assistance of an external clinician programmer computer system, which would allow the clinician to set the compliance monitor bits (and/or write the pulse and aggregate programs), and wirelessly transmit the program(s) to the memory circuitry in the IPG 10. See, e.g., U.S. Patent Application Publication 2015/0360038 (disclosing a clinician programmer for setting or adjusting a patient's stimulation therapy). A compliance monitor bit may also be set automatically by the IPG 10 or the external programmer software. For example, the IPG 10 (e.g., aggregate logic 516; FIG. 4A) may realize that a particular aggregate program has certain particularly high amplitude pulses, and may set the compliance monitor bit with instructions for those pulses. In this regard, note that the compliance monitoring instructions can be defined in data structures other than the pulse programs depicted in FIG. 5B.

FIG. 6A shows further details concerning integration of compliance voltage monitoring and adjustment in ASIC 160. As shown, the voltage at the electrodes nodes 61 a (VE1, VE2, etc.) are reported along analog bus 67 from the DAC circuitry 172 to compliance circuitry 199, which in one example comprises a compliance detector 201 and compliance logic 220, as depicted in further detail with respect to FIGS. 6B-6D. Circuitry 199 also receives the compliance monitor bits instructions with the appropriate timing when issued from the aggregate logic 516 that is executing an aggregate program, hence providing stimulation pulses to the patient. Aggregate logic 516 further provides to compliance circuitry 199 information regarding which electrodes are currently—during the pulse phase in which the compliance monitor bit is specified—acting as anodes and cathodes. This allows the circuitry 199 to understand which electrode node voltages are relevant to monitor when a compliance monitoring bit instruction issues, as explained further below. If compliance circuitry 199 determines from the compliance voltage measurements that the compliance voltage VH is too high or too low, it can issue a compliance voltage interrupt (Int(VH)) to the microcontroller block 150, which can in turn take certain actions as discussed in further detail with respect to FIGS. 7A-7C. Note that interrupt Int(VH) can be communicated to the microcontroller block 150 either via the internal bus 192, or directly and independently of the bus.

FIG. 6B shows further details of the compliance detector 201 within compliance circuitry 199. The compliance detector 201 effectively determines the voltage drops across the active PDAC and NDAC circuitry, akin to Vp and Vn as shown in FIG. 3, although such voltage drops may not be directly measured by compliance detector circuitry 201 (although they could be). Instead, and as shown below, these voltage drops are inferred by assessing the voltages at the active electrode nodes 61 a, VEx, and scaling their values to appropriate levels for comparison to various reference values to determine whether they are high or low—and hence whether the voltage drops across the PDACs or NDACs are high or low.

Compliance detector 201 receives the electrode node voltages and inputs each into an anode window comparator 208 p and a cathode window comparator 208 n. Anode window comparators 208 p receive anode high and low reference voltages, Vp(ref)H and Vp(ref)L, between which is a desired range for the input electrode node voltages when they are operating as anodes. If an anode electrode node voltage (e.g., VE1) is too high (>Vp(ref)H), the anode window comparator 208 p will output an anode high signal (e.g., Vp1H=‘1’) to compliance logic circuitry 220, described in further detail with respect to FIG. 6C. If an anode electrode node voltage is too low (<Vp(ref)L), the anode window comparator 208 p will output an anode low signal (e.g., Vp1L=‘1’) to compliance logic circuitry 220. Cathode window comparators 208 n receive cathode high and low reference voltages, Vn(ref)H and Vn(ref)L, between which is a desired range for the input electrode node voltages when they are operating as cathodes. If a cathode electrode node voltage (e.g., VE1) is too high (>Vn(ref)H), the cathode window comparator 208 n will output a cathode high signal (e.g., Vn1H=‘1’), or if too low (<Vn(ref)L), the cathode window comparator 208 n will output a cathode low signal (e.g., Vn1L=‘1’).

Thus, the window comparators 208 can establish four digital signals (e.g., Vp1H, Vp1L, Vn1H, Vn1L) for each electrode node voltage (e.g., VE1), depending whether that electrode is operating as an anode or cathode, and whether the voltage is too high or too low. Together, these four signals for all of the electrodes comprise a high/low bus 210 received by the compliance logic 220.

The anode and cathode high and low reference voltages are formed by a window reference voltage generator 202. Generator 202 comprises an op amp 204, which receives a reference voltage, such as a 1V. Op amp 204 outputs to a transistor 206 which is serially connected by an upper resistor Rp to the compliance voltage VH, and by a lower resistor Rn to ground. Feedback establishes the reference voltage (1V) across the lower resistor, Rn, and because Rp=Rn, the reference voltage is also dropped across the upper resistor Rp. The upper and lower resistors Rp and Rn comprise a number of taps 203, which taps can be selected to operate as the reference voltages used by the window comparators 208 p and 208 n. More specifically, window comparator width control signals <W> choose a pair of anode reference voltages and a pair of cathode reference voltages. The pair chosen establishes a smaller or larger desired range of acceptable voltages for the input electrode nodes at the window comparators. For example, if Vp(ref)H3/L3 and Vn(ref)H3/L3 are chosen, the windows are relatively small; therefore, VpxH and VpxL and VnxH and VnxL are more likely to be asserted by the window comparators. By contrast, if Vp(ref)H1/L1 and Vn(ref)H1/L1 are chosen, the windows are relatively big; therefore, VpxH and VpxL and VnxH and VnxL are less likely to be asserted by the window comparators. Why it may be warranted to vary the window comparator width via control signals <W> is discussed further below.

The anode and cathode high and low reference voltages are preferably symmetric with respect to VH and the reference voltage. For example, if Vn(ref)H2=0.6V and Vn(ref)L2=0.4V, then Vp(ref)H2 is preferably VH−0.4V and Vp(ref)L2 is preferably VH−0.6 V.

The electrode node voltages VEx are preferably adjusted by capacitors before being provided to the inputs of the individual comparators in each window comparator. At the anode window comparators 208 p, the capacitors reference the electrode voltages to the compliance voltage, VH, thus making this input to the comparators depend on VH, which can vary. This is important, because the anode high and low reference voltages provided by the generator 202 to the anode window comparators 208 p are also dependent on VH. VH variation is less important as concerns the cathode window comparators 208 n, because the cathode high and low reference voltages provided by the generator 202 are held steady by the reference voltage (e.g., 1V). Nonetheless, symmetrical referencing of the electrode node voltages to ground by the capacitors ensures that the voltage inputs into the comparators are of the right magnitude compared to the cathode high and low reference voltages. Resistors could be used as well as capacitors to adjust the values of the electrode node voltages.

As shown in FIGS. 6B and 6C, the compliance logic 220 receives the compliance monitor bits instructions when issued, and further receives information regarding which electrodes are currently acting as anodes and cathodes. This allows compliance logic 220 to know when to sample the signals on the high/low bus 210, and which of those signals are relevant at any given time.

The compliance logic 220 is shown in detail in FIG. 6C, and as just mentioned, it receives the signals on the high/low bus 210 indicating whether particular electrode node voltages are high, low, or neither at the moment. Essentially, the compliance logic 220 employs an algorithm to decide when the compliance voltage, VH, may need adjustment, and issues interrupt Int(VH) to the microcontroller 150 as stated above. As discussed in detail below, the compliance logic's algorithm employs sophistication to issue the interrupt sensibly, and preferably doesn't issue the interrupt whenever a single high or low signal is issued on the high/low bus 210.

As FIG. 6C shows, the high/low signals on bus 210 are processed by two different logic blocks: an over-compliance logic block 222 and an under-compliance logic block 224. When a compliance monitor bit (CMB) instruction issues, logic blocks 222 and 224 sample the high/low signals corresponding to the currently active anodes and cathodes, and employ rules to decide whether to increments counters 226 and 228. If all anodes are high, or if all cathodes are high, then the over-compliance logic block 222 increments a high counter 226. By contrast, if at least one anode is low and at least one cathode is low, then the under-compliance logic block 224 increments a low counter 228. The rationale for the rules employed by the logic blocks 222 and 224 relate to the interdependence of the PDAC and NDAC circuitry in forming pulses. In any event, other rules could operate within the logic blocks 222 and 224.

FIG. 6D shows an example explaining operation of the logic blocks 224 and 224 and counters 226 and 228. Compliance monitoring bits are issued at times t1-t11, and generally correspond to the compliance monitor bits established in timing channels 1 (TC1; FIG. 5A) and 2 (TC2; FIG. 5D) illustrated earlier. The table shows relevant high/low signals from bus 210. Because TC1 only involves electrode node E1 as an anode and E2 as a cathode, only high/low signals Vp1H, Vp1L, Vn2H, and Vn2L are relevant and considered by the logic blocks 222 and 224 when CMB instructions issue in TC1. Because TC2 only involves electrode node E4 as an anode and E5 and E6 as cathodes, only high/low signals Vp4H, Vp4L, Vn5H, Vn5L, Vn6H, and Vn6L are relevant and considered by the logic blocks 222 and 224 when CMB instructions issue in TC2. As mentioned above, aggregate logic 516 can inform compliance logic 220, and blocks 222 and 224 in particular, which electrode node voltages are current active as anodes and cathodes.

At time t1, a CMB instruction issues in TC2, and the voltage at anode E4 is high (Vp4H=‘1’). E4 is the only anode active at the time, and hence all anodes are high, meeting over-compliance block 222's rule, and thus incrementing high counter 226.

At time t2, a CMB instruction issues in TC1, and the voltage at anode E1 is high (Vp1H=‘1’). E1 is the only anode active at the time, and hence all anodes are high, meeting over-compliance block 222's rule, and thus incrementing high counter 226 again.

At time t3, a CMB instruction issues in TC1, and the voltage at cathode E2 is low (Vn2L=‘1’). But no anodes (E1) are low. This does not meet under-compliance block 224's rule, and thus low counter 228 is not incremented.

At time t4, a CMB instruction issues in TC2, and the voltage at cathodes E5 and E6 are low (Vn5L=Vn6L=‘1’). But no anodes (E4) are low. This does not meet under-compliance block 224's rule, and thus low counter 228 is not incremented.

At time t5, a CMB instruction issues in TC1, and the voltage at anode E1 is low (Vp1L=‘1’) and the voltage at cathode E2 is low (Vn2L=‘1’). This meets under-compliance block 224's rule, and thus low counter 228 is incremented.

At time t6, a CMB instruction issues in TC2, and the voltage at cathode E5 is high (Vn5H=‘1’). There is however another cathode E6, and it is not high. This does not meet over-compliance block 222's rule, and thus high counter 226 is not incremented.

At time t7, a CMB instruction issues in TC1, and the voltage at cathode E2 is high (Vn2H=‘1’). E2 is the only cathode active at the time, and hence all cathodes are high, meeting over-compliance block 222's rule, and thus incrementing high counter 226.

At time t8, a CMB instruction issues in TC2, and the voltage at cathodes E5 and E6 are high (Vn5H=Vn6H=‘1’). These are all of the active cathodes, meeting over-compliance block 222's rule, and thus incrementing high counter 226.

At time t9, a CMB instruction issues in TC1, and the voltages at anode E1 and cathode E2 are neither high nor low (all=‘0’). Hence, neither block 222 nor block 224's rules are met, and neither of counters 226 and 228 are incremented.

At time t10, a CMB instruction issues in TC1, and the voltages at anode E1 and cathode E2 are high (Vp1H=V2 nH=‘1’). This meets over-compliance block 222's rule (for two reasons), and thus high counter 226 is incremented.

At time t11, a CMB instruction issues in TC2, and the voltage at sole anode E4 is low (Vp4L=‘1’), and the voltages at cathode E5 is low (Vn5L=‘1’). This meets under-compliance block 224's rule, even though additional cathode E6 is not low. Hence, low counter 228 is incremented.

FIG. 6D doesn't likely represent an actual use, because an IPG 10 would not ordinarily experience such frequent changes in the high/low signals on bus 210. Nonetheless, FIG. 6D does show how various combinations of high/low signals would be processed by the compliance logic 220.

Returning to FIG. 6C, the counts accumulating in the counters 226 and 228 are reported to a count threshold logic block 230. In block 230, the count in either of the counters 226 and 228 must meet or exceed a threshold value before the compliance logic 220 will issue the interrupt Int(VH) to the microcontroller 150. This is desired to keep from needlessly over-correcting the compliance voltage. It would be expected during operation of the IPG that some pulses will from time to time not issue perfectly due to noise or other factors. Such spurious occasions preferably should not by themselves give rise to an interrupt, even if they meet the rules of over- and under-compliance logic blocks 222 and 224 and cause high or low counters 226 or 228 to increment. Instead, a number of high or low counts is required to ensure that the compliance voltage is truly too high or too low, and therefore that it is worthwhile to interrupt the microcontroller 150 so that it may take action, as described subsequently.

In count threshold logic block 230, the high count threshold and the low count threshold need not be equal. Instead, in one example, the high count threshold is set to 100, meaning that the high counter 226 must equal 100 or greater before the interrupt Int(VH) is issued; whereas the low count threshold is set to 10, meaning that the low counter 228 must equal 10 or greater before the interrupt Int(VH) is issued. This difference in high and low thresholds is preferred because a compliance voltage that is too high may be considered less problematic than a compliance voltage that is too low: if the compliance voltage is too high, power may be wasted, but stimulation pulses will still be reliably issued; if the compliance voltage is too low, at least some stimulation pulses may be issued with amplitudes that are too small, hence affecting therapy. Having said this, a single threshold value in other designs could be used and applied to both high and low counts.

If the compliance logic 220 has a count that exceeds a threshold—whether high or low—the interrupt Int(VH) issues as mentioned previously. It is worth noting that to this point the disclosed technique for monitoring the compliance voltage doesn't require any assistance from the microcontroller 150. The CMB instructions are set in the memory in the stimulation circuitry 170 and automatically issued to the compliance logic 220; and the compliance detector 201 and compliance logic 220 can otherwise operate by themselves without microcontroller 150 assistance. This offloading of functionality from the microcontroller 150 simplifies system management. Further, this technique is considerate of IPG 10 power, because—from the standpoint of compliance voltage management—the microcontroller 150 is only awoken to take action when it receives an interrupt; the microcontroller 150 may otherwise remain in a low-power sleep state.

FIG. 7A shows actions the microcontroller 150 can take when it receives the compliance voltage interrupt Int(VH) from the compliance logic 220. First, the microcontroller 150 can read the high counter 226 and low counter 228 via bus 192, and can clear those registers back to a zero count. This is useful so that the microcontroller 150 can understand whether it was interrupted because of an over- or under-compliance voltage condition. However, reading the counters is not strictly necessary. For example, count threshold block 230 could in another example issue two interrupts—Int(VH)H if the high counter 226 is above its count threshold, and Int(VH)L if the low counter 228 is above its count threshold. In other words, the microcontroller 150 may receive a high interrupt and a low interrupt, and so can understand whether the compliance voltage is high or low without having to read any data from the compliance circuitry 199 220. Next, the microcontroller 150 can read the current value for the compliance voltage, VH, and the battery voltage, Vbat, if it's not already known to it. This can occur by reading VH and Vbat from the A/D block (FIG. 2B).

Thereafter, the microcontroller 150 can command the VH generator 76 (FIG. 2B) as to how to adjust the compliance voltage VH it generates. Such command may be relatively simple: for example, if the compliance voltage is too low (as evidenced by low counter 228), the microcontroller 150 can command the VH generator 76 to increase the compliance voltage, perhaps by some set minimal amount or increment (e.g., 0.5V); if the compliance voltage is too high (as evidenced by high counter 226), the microcontroller 150 can command the VH generator 76 to decrease the compliance voltage, again perhaps by some set amount or increment. The compliance voltage monitoring functions described above can continue to run to verify the effectiveness of the compliance voltage adjustment, and the process may be repeated if the compliance voltage needs further adjustment.

Still referring to FIG. 7A, adjustment to the VH generator 76 may be assisted through the use of VH adjustment data 240, which is preferably stored with the microcontroller 150. Such VH adjustment data 240 may depend on the way the VH generator 76 is built, and two different ways are illustrated in FIGS. 7B and 7C. In FIG. 7B, the VH generator 76 comprises an inductor-based boost circuit, which as is known boosts the battery voltage Vbat to the compliance voltage VH using a pulse width modulator 80 to vary the duty cycle (DC) of a gating signal 81 that controls the converter. Increasing the duty cycle—i.e., the amount of time that the gating signal 81 is on relative to its period—generally increases the compliance voltage VH. See, e.g., U.S. Patent Application Publication 2015/0134029 (discussing boost converter circuitry in further detail). Accordingly, VH adjustment data 240 may not be needed in this design, as the microcontroller 150 can merely command the VH generator 76 to increase or decrease its duty cycle depending whether VH should be increased or decreased.

In FIG. 7C, the VH generator 76 comprises a capacitor-based charge pump. See e.g., U.S. Pat. Nos. 8,219,196; 9,233,254; 7,805,189. In this example, the VH generator 76 comprises a number of capacitors (e.g., C1-C4) that can be charged to the battery voltage, Vbat, during a first clock (CLK1), and then connected together during a second clock cycle in various manners to form various compliance voltages values. The capacitors are connectable by various switches controlled by switch control signals <S> (e.g., S1, S2, etc.). Just a few example switches are shown in FIG. 7C, which are controlled by switch control signals S1 and S2 to respectively either connect capacitors C1 and C2 in parallel or in series. Still other switches and switch control signals would be used to establish various connections to capacitors C3 and C4. A few example configurations of the capacitors are shown: for example, a configuration is shown in which all capacitors are connected by the switches in series (forming VH=5 Vbat), which configuration is arrived at by setting the switch control signals with particular values. As one skilled will appreciate, the various switch configurations will establish various compliance voltages VH that comprise fractional multiples of the battery voltage. Microcontroller 150, once interrupted, can command the VH generator 76 to use a different switch configuration to adjust the compliance voltage, VH.

When dealing with a VH generator 76 of this type, VH adjustment data 240 may be useful, and as shown may comprise a table relating the compliance voltage VH with a particular battery voltage and switch configuration. Further, data 240 may associate a maximum current, IH(max), with each configuration. The maximum current providable by each capacitor configuration will depend on the size of the capacitances and the manner in which they are connected. This can be important to assist the microcontroller 150 in deciding how to command the VH generator 76.

For example, assume that it is determined that VH should be increased, and that the compliance voltage VH is currently set by the VH generator 76 at ‘A’, with a switch configuration 3 that establishes VH=2 Vbat. In one example, the microcontroller 150 may increase VH by simply commanding the VH generator 76 to use the next-highest switch configuration 4 for VH in VH adjustment data 240—i.e., ‘B,’ which will increase VH to (7/3)Vbat. However, the microcontroller 150 may also not simply pick the next-highest or lowest switch configuration for the VH generator 76. For example, the microcontroller 150 may realize that stimulation pulses running in the active timing channel(s) are of a relatively large amplitude. If this is the case, commanding the VH generator 76 to use switch configuration 4 (‘B’) may not be wise, as the maximum current IH(max) producible in this configuration decreases from 2.5 mA (‘A’) to 2.0 mA (‘B’). Commanding the VH generator 76 to use configuration ‘B’ might run the risk that the compliance voltage VH will become loaded and unable to form the pulses. Thus, the microcontroller 150 may instead command the VH generator 76 to use switch configuration 5 (‘C’). This produces an even higher compliance voltage (VH=(5/2)Vbat), but more importantly provides a compliance voltage with a larger maximum current. To summarize, VH adjustment data 240 can include data indicative of the operation of the VH generator 76 to allow the microcontroller 150 to adjust compliance voltage VH in an informed manner.

As shown in FIG. 7A, along with commanding the VH generator 76 how to adjust the compliance voltage VH, the microcontroller block 150 may also issue the window comparator width control signals <W> mentioned earlier. More specifically, the microcontroller block 150 may via bus 192 write values for the control signals <W> to registers included within the compliance detector 201 and compliance logic 220 (FIG. 6A). As mentioned earlier, control signals <W> can be used to set a wide or narrow desired range of acceptable voltages for the window comparators 208 p and 208 n (FIG. 6B), thus making it respectively less or more likely that high/low signals will be asserted on the bus 210, and hence through operation of the compliance logic 220 (FIG. 6C) that a compliance voltage interrupt Int(VH) will issue.

There are different reasons why the microcontroller 150 may adjust the window comparator width control signals <W>. In one example, the microcontroller 150, after adjusting VH, may initially set <W> to a wide value, and then narrow <W> over time. This will reduce the search time need to establish the compliance voltage VH, and yet deliver an accurate value for VH to save power. In another example, the width may be set based on the amount that VH is adjusted. For example, if a capacitor-based charge pump is used for VH generator 76 (FIG. 7C), VH may be adjusted a small amount—e.g., from (5/4)*Vbat to (4/3)*Vbat, in which case it may only be necessary to widen the comparator windows 208 p and 208 n by a small amount. By contrast, a larger adjustment, say from 4 Vbat to 5 Vbat, may warrant widening the comparator windows by a larger amount. The width of the comparator windows may also be scaled in accordance with the battery voltage, Vbat, because VH is ultimately a function of Vbat when a capacitor based charge pump is used. Finally, the number of capacitors used in the charge pump may have an effect on the manner in which the microcontroller 150 sets the width of the comparator windows via control signal <W>. For example, if fewer capacitors were used, the steps in VH creatable by the change pump could be larger, and hence <W> might logically be set to wider values.

While disclosed in the context of a particular design for the stimulation circuitry 170 and DAC circuitry 172, the invention isn't so limited. Also, while disclosed in the context of an implantable pulse generator, the improved compliance voltage monitoring and adjustment circuitry could also be implemented in a non-implantable pulse generator, such as an External Trial Stimulator (ETS). See, e.g., U.S. Pat. No. 9,259,574 (describing an ETS).

Although particular embodiments of the present invention have been shown and described, the above discussion is not intended to limit the present invention to these embodiments. It will be obvious to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the present invention. Thus, the present invention is intended to cover alternatives, modifications, and equivalents that may fall within the spirit and scope of the present invention as defined by the claims. 

What is claimed is:
 1. A pulse generator, comprising: electrode nodes, wherein each of the electrode nodes is configured to be coupled to one of a plurality of electrodes in contact with a patient's tissue; stimulation circuitry comprising first memory locations configured to store data for consecutive first phases of a first stimulation pulse in consecutive ones of the first memory locations; digital-to-analog converter (DAC) circuitry configured to form the consecutive first pulse phases at selected ones of the electrode nodes, wherein the DAC circuitry is powered by a compliance voltage; and compliance circuitry configured to process voltages at the electrode nodes to determine whether to adjust the compliance voltage; wherein at least some of the first memory locations are each formatted to include compliance voltage monitoring data along with the data for one of the first pulse phases, wherein the compliance voltage monitoring data is configured to be set or not set with an instruction, wherein the instruction is configured to instruct the compliance circuitry to process the voltages at the selected electrode nodes during the first pulse phase whose data is stored in one of the first memory locations with the instruction.
 2. The pulse generator of claim 1, wherein the compliance voltage monitoring data comprises a single bit, wherein the single bit is set with the instruction when set to a first logic state, and wherein the single bit is not set with the instruction when set to a second logic state.
 3. The pulse generator of claim 1, wherein the compliance circuitry comprises detector circuitry, wherein the detector circuitry is configured to process the voltages at the selected electrode nodes by generating a high signal and a low signal for each selected electrode node, wherein the high signal for each selected electrode node is asserted when the voltage at that selected electrode node is high, and wherein the low signal for each selected electrode node is asserted when the voltage at that selected electrode node is low.
 4. The pulse generator of claim 3, wherein the compliance circuitry further comprises logic circuitry, wherein the high and low signals are processed at the logic circuitry to determine whether to adjust the compliance voltage.
 5. The pulse generator of claim 4, wherein the logic circuitry comprises an over-compliance logic block having a first output and configured to receive the high signals for the selected electrode nodes, wherein the over-compliance block applies a first rule to the high signals, wherein the first output is asserted if the first rule is met, and an under-compliance logic block having a second output and configured to receive the low signals for the selected electrode nodes, wherein the under-compliance block applies a second rule to the low signals, wherein the second output is asserted if the second rule is met.
 6. The pulse generator of claim 5, wherein the logic circuitry further comprises a high counter configured to receive the first output, wherein a count of the high counter is incremented when the first output is asserted, and a low counter configured to receive the second output, wherein a count of the low counter is incremented when the second output is asserted.
 7. The pulse generator of claim 6, wherein the logic circuitry further comprises a count threshold block, wherein the logic circuitry is configured to determine to adjust the compliance voltage if the count of the high counter exceed a first threshold or if the count of the low counter exceeds a second threshold.
 8. The pulse generator of claim 1, further comprising a microcontroller block, wherein the compliance circuitry is further configured to issue an interrupt to the microcontroller block if the compliance circuitry determines to adjust the compliance voltage.
 9. The pulse generator of claim 8, further comprising a compliance voltage generator configured to produce the compliance voltage, wherein the microcontroller block is further configured to issue a command to the compliance voltage generator to adjust the compliance voltage in response to receiving the interrupt.
 10. The pulse generator of claim 8, wherein the electrode nodes, the stimulation circuitry, the DAC circuitry, the compliance circuitry, and the microcontroller block are integrated on a single integrated circuit.
 11. The pulse generator of claim 1, wherein the first stimulation pulse comprises a biphasic pulse including a stimulation phase and an active recovery phase, wherein the compliance voltage monitoring data is set with the instruction for the stimulation phase, but wherein the compliance voltage monitoring data is not set with the instruction for the active recovery phase.
 12. The pulse generator of claim 1, wherein the stimulation circuitry further comprises a compliance monitoring timing register, wherein the compliance monitoring timing register specifies a time during the first pulse phase when the compliance voltage instruction will instruct the compliance circuitry to process the voltages at the selected electrode nodes.
 13. The pulse generator of claim 1, wherein at least some of the first memory locations are not formatted to include compliance voltage monitoring data along with the data for one of the first pulse phases.
 14. The pulse generator of claim 1, wherein the stimulation circuitry further comprises second memory locations configured to store data for consecutive second phases of a second stimulation pulse in consecutive ones of the second memory locations, wherein the DAC circuitry is further configured to form the consecutive second pulse phases at the selected ones of the electrode nodes, wherein at least some of the second memory locations are each formatted to include the compliance voltage monitoring data along with the data for one of the second pulse phases, and wherein the compliance voltage monitoring data is set with the instruction for at least one of the first pulses phases, but wherein the compliance voltage monitoring data is not set with the instruction for any of the second pulse phases.
 15. The pulse generator of claim 1, further comprising at least one implantable lead, wherein the electrodes are located on the at least one implantable lead.
 16. A pulse generator, comprising: electrode nodes, wherein each of the electrode nodes is configured to be coupled to one of a plurality of electrodes in contact with a patient's tissue; stimulation circuitry configured to store first data defining a first pulse shape and second data defining a second pulse shape, and for configuring a pulse train comprising one or more first pulses followed by one or more second pulses, wherein the first and second data are formatted to include compliance voltage monitoring data, wherein the compliance voltage monitoring data is configured to be set or not set with an instruction, wherein the instruction is configured to instruct the taking of at least one measurement used to determine whether to adjust the compliance voltage; and digital-to-analog converter (DAC) circuitry configured to form the pulse train at selected ones of the electrode nodes, wherein the DAC circuitry is powered by the compliance voltage.
 17. The pulse generator of claim 16, wherein the compliance voltage monitoring data is set with the instruction in the first data, but wherein the compliance voltage monitoring is not set with the instruction in the second data.
 18. The pulse generator of claim 16, wherein the at least one measurement used to determine whether to adjust the compliance voltage comprises processing of voltages at the selected electrode nodes.
 19. The pulse generator of claim 16, wherein the first data comprises data for a plurality of consecutive first pulse phases defining the first pulse shape, and wherein the second data comprises data for a plurality of consecutive second pulse phases defining the second pulse shape, wherein the first data is formatted to include the compliance voltage monitoring data with at least some of the data for the first pulse phases, and wherein the second data is formatted to include the compliance voltage monitoring data with at least some of the data for the second pulse phases.
 20. The pulse generator of claim 16, further comprising compliance circuitry configured to receive the at least one measurement, wherein the compliance circuitry is configured to issue at least one interrupt if the compliance circuitry determines to adjust the compliance voltage.
 21. The pulse generator of claim 16, further comprising at least one implantable lead, wherein the electrodes are located on the at least one implantable lead. 